Repository navigation
Conversation
GITHUB_TOKEN can no longer create pull requests in the org; mint a token from the sdk-bot environment instead of re-enabling that setting. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Loschcode
requested review from
JimmyPettersson85,
oliverlaz and
szuperaz
as code owners
November 20, 2026 16:22
Contributor
|
Hold until getstream-sdk-bot is installed on this repo, and on GetStream/chat and GetStream/protocol. It is not installed yet: today's regen runs fail with a 404 on the App installation lookup. Merging before that just moves the failure to the release job. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
The 2026-11-20 org hardening turned off "Allow GitHub Actions to create and approve pull requests", so release-please can no longer open Release PRs with
GITHUB_TOKEN(e.g. stream-sdk-java run 44715449332). We're keeping that org setting off: it would also letGITHUB_TOKENapprove PRs, which bypasses review.What
release-pr.ymlnow opens the Release PR as getstream-sdk-bot, the like the other server-side SDKs; stream-node-release-bot was uninstalled in the same cleanup:sdk-botenvironment (key stays branch-restricted there), scoped tocontents+pull-requestswrite onlyGITHUB_TOKENin this job drops tocontents: read(unchanged)GITHUB_TOKENonesHotfix branches (
N.x) aren't allowed by thesdk-botenvironment, so there the job runs without the key on a read-only token. A push with nothing to release stays green. One with changes fails until the environment allows that branch. That path is already broken by the org setting, so this isn't a regression.Depends on
getstream-sdk-bot being reinstalled on this repo (it was uninstalled in the same cleanup).
Verify after merge
The next push to main → Release PR opened/updated by
getstream-sdk-bot[bot].🤖 Generated with Claude Code